I need help with setting DOORS Login Policy via batch. I need to switch DOORS access from System Usernames (compatible with our Common Access Cards [CAC]) and Username/Password to support communication with IBM's Integration software for HP Quality Center. The Login Policy is set (via DXL batch) using the setLoginPolicy to "Use passwords" (checkbox shown on the Login Policy tab) for IBM's integration software to access DOORS during the evening via username and password (which is the only way the integration software works) and then run a batch DXL to set the Login Policy back to "Use system usernames" so users can access DOORS based on Active Directory username (DOORS system usernames) associated with their CACs. I've tried a DXL script but the checkboxes are not changing as a result. The declaration statement is: void setLoginPolicy (LoginPolicy policy) where policy is either viaDOORSLogin or viaSystemLogin (which should set the checkboxes mentioned and shown in the attachment). I work with DXL but have done little to set database variables. Help please!!! ... I have had a ticket into IBM for over a month with still no resolution. I used to set settings at the database backend through dbadmin.exe and IBM has found a known issue with settings not working as expected that resulted from changes made sometime after DOORS Version 9.4. They provided a solution which doesn't work for me. Then the rep closed the ticket. I wasted countless hours finding the problem with database settings on the backend but still have no solution so I've shifted for a front end solution (via the application interface). Can someone who is used to functions and setting database characteristics via the application front end please help? Thank you for any suggestions you may have! TessR - Wed Jun 03 18:27:26 EDT 2015 |
Re: Using setLoginPolicy and getLoginPolicy to support common access card (CAC) access It seems you need to call the saveDirectory perm to make the setting persist. Try: setLoginPolicy viaSystemLogin string sErr = saveDirectory() print "Msg: " sErr "\n" However this seems the be a weird workaround for getting an integration to work. I am sure, that there is a trick that you can apply to get the integration also working without this. Regards, Mathias
|